Storage system and data management method

ABSTRACT

A storage system and data management method is provided that improves the reliability and fault tolerance of the hard disks saving data utilizing an AOU function. 
     A storage system comprises a first correlating section for correlating a plurality of RAID groups composed of a plurality of physical disks, and the pool region, a second correlating section for correlating the pool region and the storage regions of the virtual volumes, a first allocation section for allocating first data from the host apparatus to the first storage region of the first RAID group based on write requests from the host apparatus, and a second allocation section for distributing second data from the host apparatus at and allocating the second data to any storage regions of the RAID group, with the exception of the first storage region of the first RAID group allocated by the first allocation section, based on write requests.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application relates to and claims priority from Japanese PatentApplication No. 2007-015358, filed on Jan. 25^(th), 2007, the entiredisclosure of which is incorporated herein by reference.

BACKGROUND

1. Field of the Invention

The present invention relates to a storage system and data managementmethod that is particularly appropriate for application to storagesystems ensuring reliability and fault tolerance for stored data.

2. Description of Related Art

In the related art, a method of managing a plurality of hard disks usinga RAID (Redundant Array of Independent/Inexpensive Disks) exists forstorage systems managing data using storage apparatus. At least one ormore logical volumes (hereinafter referred to as “logical volumes”) areformed on a physical storage region provided by a large number of harddisks.

Of the RAID methods, for example, a method referred to as RAID1 existsto ensure that data is not lost from the host apparatus even if one harddisk fails. In this method, the host apparatus accesses one virtuallogical volume (hereinafter referred to as “virtual volume”) but inreality adopts a method where the same data is stored on respective harddisks constituted by two hard disks. According to this method, it ispossible to ensure data redundancy.

Further, other technology for providing data redundancy is disclosed inpatent document 1 where technology is provided where a module isequipped with a plurality of data storage sections comprised of sliceregions formed in advance in order to store sliced data, a managementinformation storage section for managing the slice regions, and acommunication function section for communicating sliced data stored inthe data storage sections and management information for storing withinthe management information section.

On the other hand, technology referred to as a so-called AOU (AllocationOn Use) function where virtual volumes are supplied to a host apparatuswithout making logical volumes of fixed capacities from storage regionsof a hard disk and where storage regions of a hard disk are dynamicallyallocated to virtual volumes according to requests from the hostapparatus is also proposed. According to technology using this AOUfunction, it is possible to dynamically extend the capacity of a virtualvolume.

[Patent Document 1]

International publication pamphlet number 2004/104845

However, with the RAID 1 method referred to as mirroring, two hard disksare written to at the same time when data is written to a virtualvolume. This means that the hard disk of the smaller capacity has to becatered for in the event that the capacity of the two hard disks isdifferent.

Further, on the other hand, in the event that a fault occurs wherefunctioning as a RAID group no longer takes place, with a storage systemthat does not utilize an AOU function, it is no longer possible to uselogical volumes belonging to this group, but with storage systemsutilizing an AOU function, it is no longer possible to use virtualvolumes where regions are allocated from the RAID group. There istherefore the problem that storage systems utilizing an AOU functionexert substantial influence on the system as a whole compared withstorage systems that do not utilize and AOU function.

The present invention therefore sets out to provide a storage system anddata management method that utilizes an AOU function and improvesreliability and fault tolerance of a hard disk saving data.

SUMMARY

In order to resolve these problems, in an aspect of the presentinvention, a storage system allocating some or all of storage regionssupplied by physical disks storing data from host apparatus as a poolregion, and forming virtual volumes dynamically allocated from the poolregions comprises a first correlating section for correlating aplurality of RAID groups composed of a plurality of physical disks, andthe pool region, a second correlating section for correlating the poolregion and the storage regions of the virtual volumes, a firstallocation section for allocating first data from the host apparatus tothe first storage region of the first RAID group based on write requestsfrom the host apparatus, and a second allocation section fordistributing second data from the host apparatus at and allocating thesecond data to any storage regions of the RAID group, with the exceptionof the first storage region of the first RAID group allocated by thefirst allocation section, based on write requests from the hostapparatus.

As a result, it is possible to dynamically provide virtual volumescorrelated in order to store requested data from a physical disk basedon write requests of host apparatus, and it is possible to distributeconsecutive data from the host apparatus to a plurality of RAID groupsfor storage.

Further, in the present invention, a data management method for astorage system allocating some or all of storage regions supplied byphysical disks storing data from host apparatus as a pool region, andforming virtual volumes dynamically allocated from the pool regionscomprises a first correlation step of correlating a plurality of RAIDgroups composed of a plurality of the physical disks, and the poolregion, a second correlation step of correlating the pool region and thestorage regions of the virtual volumes, a first allocation step ofallocating first data from the host apparatus to the first storageregion of the first RAID group based on write requests from the hostapparatus, and a second allocation step of distributing second data fromthe host apparatus at and allocating the second data to any storageregions of the RAID group, with the exception of the first storageregion of the first RAID group allocated in the first allocation step,based on write requests from the host apparatus.

As a result, it is possible to dynamically provide virtual volumescorrelated in order to store requested data from a physical disk basedon write requests of host apparatus, and it is possible to distributeconsecutive data from the host apparatus to a plurality of RAID groupsfor storage.

According to the present invention, by utilizing an AOU function, it ispossible to improve the reliability and fault tolerance of hard diskssaving data.

Other aspects and advantages of the invention will be apparent from thefollowing description and the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block view showing an overall configuration for a storagesystem of a first embodiment;

FIG. 2 is a schematic showing in a channel adapter of the firstembodiment;

FIG. 3 is a schematic showing in a disk adapter of the first embodiment;

FIG. 4 is an outline view showing a logical configuration for a storagesystem of the first embodiment;

FIG. 5 is a schematic showing in shared memory of the first embodiment;

FIG. 6 is a schematic showing configuration information for the hostvolume of the first embodiment;

FIG. 7 is a schematic showing configuration information for the virtualvolume and the pool volume of the first embodiment;

FIG. 8(A) and FIG. 8(B) are schematic showing configuration informationfor a virtual volume of the first embodiment;

FIG. 9 is a schematic showing configuration information for a poolvolume of the first embodiment;

FIG. 10 is a schematic showing configuration information for a page ofthe first embodiment;

FIG. 11 is a flowchart showing write processing of a channel adapter ofthe first embodiment;

FIG. 12 is a flowchart showing write processing of a disk adapter of thefirst embodiment;

FIG. 13 is a schematic showing various configuration information of thefirst embodiment;

FIG. 14 is a flowchart showing allocation processing of a channeladapter of the first embodiment;

FIG. 15 is a flowchart showing allocation and deciding processing of achannel adapter of the first embodiment;

FIG. 16 is a further flowchart showing allocation and decidingprocessing of a channel adapter of the first embodiment;

FIG. 17 is a schematic view illustrating allocation and decidingprocessing of a channel adapter of the first embodiment;

FIG. 18 is a flowchart showing fault processing of a disk adapter of thefirst embodiment;

FIG. 19 is a schematic view illustrating fault processing of a diskadapter of the first embodiment;

FIG. 20 is a flowchart showing fault recovery processing of a diskadapter of the first embodiment;

FIG. 21 is a further flowchart showing fault recovery processing of adisk adapter of the first embodiment;

FIG. 22 is a flowchart showing main processing for fault recovery of adisk adapter of the first embodiment;

FIG. 23 is a schematic view illustrating fault recovery processing of adisk adapter of the first embodiment;

FIG. 24 is a flowchart showing read processing of a channel adapter ofthe first embodiment;

FIG. 25 is a flowchart showing read processing of a disk adapter of thefirst embodiment;

FIG. 26 is a flowchart showing read sorting processing of a channeladapter of the first embodiment;

FIG. 27 is a further flowchart showing read sorting processing of achannel adapter of the first embodiment;

FIG. 28 is an outline view illustrating read sorting processing of achannel adapter of the first embodiment;

FIG. 29 is a flowchart showing addition allocation processing of a diskadapter of the first embodiment;

FIG. 30 is a further flowchart showing addition allocation processing ofa disk adapter of the first embodiment;

FIG. 31 is a schematic view of various configuration informationillustrating addition allocation processing of a disk adapter of thefirst embodiment;

FIG. 32 is an outline view illustrating addition allocation processingof a disk adapter of the first embodiment;

FIG. 33 is a schematic showing in shared memory of a second embodiment;

FIG. 34 is an outline view showing a logical configuration for a storagesystem of the second embodiment;

FIG. 35 is a flowchart showing write processing of a channel adapter ofthe second embodiment;

FIG. 36 is a flowchart showing write processing of a disk adapter of thesecond embodiment;

FIG. 37 is a further flowchart showing allocation and decidingprocessing of a channel adapter of the second embodiment;

FIG. 38 is another flowchart showing allocation and deciding processingof a channel adapter of the second embodiment;

FIG. 39 is a block view showing an overall configuration for a storagesystem of a third embodiment;

FIG. 40 is a schematic showing in a channel adapter of the thirdembodiment;

FIG. 41 is an outline view showing a logical configuration for a storagesystem of the third embodiment;

FIG. 42 is a flowchart showing copy processing of a channel adapter ofthe third embodiment; and

FIG. 43 is a flowchart showing copy processing of a channel adapter ofthe third embodiment.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following is a description with reference to the drawings below of afirst embodiment of the present invention.

(1) First Embodiment (1-1) Configuration of Storage System of the FirstEmbodiment

In FIG. 1, numeral 1 is the whole of a storage system of thisembodiment. This storage system 1 is configured from host apparatus 2connected to storage apparatus 4 via a network 3.

The host apparatus 2 is computer apparatus equipped with informationprocessing resources such as a CPU (Central Processing Unit) and memoryetc., and is configured from, for example, a personal computer,workstation, and mainframe, etc. Further, the host apparatus 2 hasinformation input apparatus (not shown) such as a keyboard, switches andpointing apparatus, and microphone etc., and also has information outputapparatus (not shown) such as a monitor display and speakers etc.

The network 3 is configured from, for example, a SAN (Storage AreaNetwork), LAN (Local Area Network), Internet, public line, or dedicatedline, etc. In the event that, for example, the network 3 is a SAN,communication between host apparatus 2 and storage apparatus 4 via thisfirst network 3 is carried out in accordance with a fiber channelprotocol, and in the event that the first network 3 is a LAN,communication is carried out in accordance with TCP/IP (TransmissionControl Protocol/Internet Protocol).

Storage apparatus 4 is comprised of a disk section 5 comprised of aplurality of hard disks 50, and a controller 6 managing the plurality ofhard disks 50 using the RAID method.

The hard disks 50 are constituted by, for example, expensive disks suchas SCSI (Small Computer System Interface) disks etc., or low-cost diskssuch as SATA (Serial AT Attachment) disks and optical disks, etc.

The controller 6 is equipped with a plurality of channel adapters 7, aconnecting section 8, shared memory 9, cache memory 10, and a pluralityof disk adapters 11, and a service processor 12.

Each channel adapter 7 is configured from a microcomputer systemequipped with a microprocessor (not shown), memory (not shown), andcommunication interface etc., and a port for connecting the network 3(not shown). Each channel adapter 7 interprets each command sent fromhost apparatus 2 and executes the necessary processing. Networkaddresses (for example, IP addresses, WWN) for providing identificationare allocated to the ports of each channel adapter 7, so that it ispossible for a channel adapter 7 to behave individually as NAS (NetworkAttached Storage).

As shown in FIG. 2, memory of each channel adapter 7 is equipped with awrite program 70 for use with channel adapter 7 managing write requestsfrom host apparatus 2, allocation program 71 for allocating data fromhost apparatus to storage regions within the hard disks 50, decidingprogram 72 for allocating to storage regions within the hard disks 50and deciding upon data from the host apparatus 2, a read program 73 foruse with channel adapter 7 for processing read requests from the hostapparatus 2, and a read sorting program 74 for sorting a plurality ofread out data in such a manner as to read out from different virtualvolumes. Each channel adapter 7 is connected with connecting section 8via an internal bus adapter (not shown).

In addition to the channel adapter 7 described above, connecting section8 is connected to shared memory 9, cache memory 10 and disk adapters 11.The exchange of data and commands with the channel adapters 7, sharedmemory 9, cache memory 10 and disk adapters 11 is carried out via thisconnecting section 8. The connecting section 8 is configured from aswitch such as, for example, an ultra-high-speed cross-bus switch fortransferring data using high-speed switching, or bus etc.

The shared memory 9 is storage memory shared by the channel adapters 7and disk adapters 11. The shared memory 9 is mainly utilized for storingsystem configuration information read from system volumes at the time ofturning on a power supply for storage apparatus 4 and various controlprograms, as well as commands etc. from host apparatus 2. Variousconfiguration information stored in shared memory 9 is described in thefollowing.

The cache memory 10 is storage memory shared by the channel adapters 7and disk adapters 11. This cache memory 10 is mainly utilized totemporarily store user data inputted to and outputted from storageapparatus 4.

Each disk adapter 11 is configured as a microcomputer system equippedwith a microprocessor (not shown) and memory (not shown) etc. andfunctions as an interface for carrying out protocol control at the timeof communication with the disk section 5. These disk adapters 11 areconnected to corresponding disk devices 61 via, for example, a fiberchannel cable, and exchange data with the disk section 5 in accordancewith a fiber channel protocol.

As shown in FIG. 3, a write program 110 for disk adapter use forprocessing write requests from the host apparatus 2, a fault program 111for processing hard disks 50 of the plurality of hard disks 50 fromwhere faults occur, a fault recovery program 112 for recovering storageregions of the hard disks 50 where faults occur, a main fault recoveryprogram 113, a disk adapter read program 114 for processing readrequests from the host apparatus 2, and an addition allocation program115 for allocating to storage regions of added hard disks 50 areprovided in the memory of each disk adapter 11.

The service processor 12 is computer apparatus operated in order tomaintain and manage the storage apparatus 4 and is, for example,configured from a note-type personal computer. At this service processor12, the host apparatus 2 is connected via the network 3, and is capableof receiving data or instructions from the host apparatus 2. The serviceprocessor 12 monitors the occurrence of faults within the storageapparatus 4 and displays these faults on a display screen (not shown).

(1-1-2) Logical Configuration for Storage System

Next, a description is given of a logical configuration for the storagesystem 1 described above.

The storage system 1 of this embodiment takes four hard disks 50 of theplurality of hard disks 50 as one ECC (Error Correcting Code) group. Oneor a plurality of logical volumes LDEV are then defined on a storageregion provided by one ECC group. An ECC group and a RAID group aredefined in this embodiment.

Of each logical volume LDEV, characteristic identifiers (LUN: LogicalUnit Number) are allocated to logical volumes LDEV designated by theuser, of each of the logical volumes LDEV. In the case of thisembodiment, the input and output of data is carried out by taking acombination of this identifier and a unique block number (LBA: LogicalBlock Address) allocated to each logical block as an address, anddesignating this address.

Here, real volumes VOL and virtual volumes VVOL exist as attributes forthe logical volumes LDEV.

Of the plurality of real volumes, pool volume PLVOL exists as the realvolume used in mapping with the virtual volumes. For example, FIG. 4 isan outline view showing a logical relationship between the hostapparatus 2 and the plurality of hard disk drives 50 of the storagesystem 1. One pool volume PLVOL may be constituted by one ECC group, ora plurality of pool volumes PLVOL may be constituted by one ECC group.

A plurality of pool volumes PLVOL may also form one pool region PL. Apool volume PLVOL may be dynamically allocated with a storage region ofthe hard disks 50 so as to supply a storage region for a virtual volumeVVOL.

A virtual volume VVOL is constituted by a host volume HVVOL accessed bythe host apparatus 2, a base volume BVVOL constituting the host volumeHVVOL, and host volume HVVOL, so as to give a mirror volume MVVOLconstituting a mirror configuration with the base volume BVVOL.

Minimum storage regions referred to as pages P that can be allocatedwith an ECC group are correlated at storage regions of base volumesBVVOL or mirror volumes MVVOL. For example, in FIG. 4, storage regionswithin base volume BVVOL or mirror volume MVVOL are made to correlatewith respective pages P0 within the ECC group 1 or ECC group 3 via poolvolume PLVOL0.

(1-2) Distributed Storage Function, Mirror Function, and AOU Function ofthis Embodiment

Next, a description is given of a distributed storage function, mirrorfunction, and AOU function mounted on the storage apparatus 4 within thestorage system 1.

A feature of this storage system 1 is to be able to decide to store datafrom the host apparatus 2 within an arbitrary ECC group based on writerequests from the host apparatus 2, and to be able to distribute storagelocations in such a manner that back-up data is stored in ECC groupsother than the ECC groups storing the data.

Here, “distributed storage function” refers to a function for storingconsecutive data in a manner distributed between a plurality of ECCgroups in the event that there is consecutive data based on writerequests from the host apparatus 2. For example, this refers to afunction where, in the event that there is consecutive data 1 to data 3,when data 1 is stored in a storage region of ECC group 1, data 2 isstored in a storage region outside of that storing the data 1, and data3 is stored in a storage region other than the storage regions storingdata 1 and data 2. There are therefore cases where the consecutive data1 to data 3 is stored in the same ECC group or in different ECC groups.

Further, a mirror function refers to a function based on a RAID 1 mirrorconfiguration. The mirror function is configured from a base volumeBVVOL and a mirror volume MVVOL.

Moreover, an AOU function refers to a function of dynamically allocatingstorage regions to base volumes BVVOL and mirror volumes MVVOL from poolregions PL or pool volumes PLVOL comprised of ECC group storage regions.

(1-2-1) Configuration Information in Shared Memory

In order to implement the functions described above, a description isgiven of the shared memory 9 of the storage apparatus 4.

At the shared memory 9, as shown in FIG. 5, host volume configurationinformation 90, virtual volume and pool volume configuration information91, virtual volume configuration information 92, pool volumeconfiguration information 93, and page configuration information 94 areprovided.

(1-2-1-1) Host Volume Configuration Information

As shown in FIG. 6, host volume configuration information 90 isconfiguration information for host volumes HVVOL recognized by the hostapparatus 2, base volumes BVVOL and mirror volumes MVVOL within thestorage apparatus 4 correlated with the volumes.

The host volume configuration information 90 is configured from a “hostvolume number” field 90A, a “base volume number” field 90B, and a“mirror volume number” field 90C.

Host volume numbers for the host volumes HVVOL accessed by the hostapparatus 2 are stored in the “host volume number” field 90A.

Volume numbers for base volumes BVVOL are stored in the “base volumenumber” field 90B. Similarly, volume numbers for mirror volumes MVVOLare stored in the “mirror volume number” field 90C.

For example, as shown in FIG. 6, a host volume of a “volume number” of“0” is constituted by a base volume of a “base volume number” of “1” anda mirror volume of a “mirror volume number” of “2”. Here, “FFFF”indicates volumes that have yet to be allocated or have not yet beenused.

(1-2-1-2) Configuration Information for Virtual Volumes and Pool Volumes

Virtual volume VVOL and pool volume PLVOL configuration information 91stores information indicating the correlation of pool volume PLVOL andvirtual volume VVOL, as shown in FIG. 7.

Virtual volume and pool volume configuration information 91 isconfigured from a “virtual volume number” field 91A, a “pool ID” field91B, and a “previously allocated ECC group index number” field 91C.

Information for numbers for virtual volumes constituting the basevolumes BVVOL and mirror volumes MVVOL is stored in the “virtual volumenumber” field 91A.

Identification numbers for pool volumes PLVOL are stored in the “poolID” field 91B. Specifically, pool ID's correlating virtual volumenumbers for base volumes BVVOL or mirror volumes MVVOL are stored.

Index numbers for ECC groups storing data for the previous time arestored in “previously allocated ECC group index number” field 91C. TheECC group index number is described using page configuration information94.

(1-2-1-3) Virtual Volume Configuration Information

As shown in FIG. 8, the virtual volume configuration information 92 isconfiguration information provided every virtual volume number assignedto a base volume BVVOL and mirror volume MVVOL, and stores informationindicating the relationship between the minimum storage region allocatedto the virtual volume and the ECC groups correlated to the storageregions.

Virtual volume configuration information 92 is configured from a “pagenumber” field 92A, “ECC group number” field 92B, and “page numberswithin an ECC group” field 92C.

Page numbers for pages (storage regions), a plurality of which areformed within a single virtual volume, are stored in the “page number”field 92A.

ECC group numbers correlated to page numbers formed within a signalvirtual volume are stored in the “ECC group number” field 92B.

Page numbers for ECC group numbers correlated with page numbers formedwithin a single virtual volume are stored in the “page numbers within anECC group” field 92C.

(1-2-1-4) Pool Volume Configuration Information

As shown in FIG. 9, pool volume configuration information 93 storesinformation indicating the number of ECC groups that are correlated withpool volume PLVOL. The configuration information 93 for the pool volumePLVOL is configured from “pool ID” field 93A and “ECC group number”field 93B.

Identification numbers for pool volumes PLVOL are stored in the “poolID” field 93A.

Pool volumes PLVOL are correlated with the “ECC group number” field 93B,and the number of ECC groups under the control of the pool volume PLVOLare stored in “ECC group number” field 93B.

For example, as shown in FIG. 9, it is shown that ECC group “3” is undercontrol at the pool volume PLVOL of “pool ID” of “0”.

(1-2-1-5) Page Configuration Information

As shown in FIG. 10, page configuration information 94 storesconfiguration information provided every pool ID that is informationindicating a correspondence relationship of pages and ECC groupsallocated within pool volume PLVOL.

The page configuration information 94 is configured from “ECC groupindex number for within a pool” field 94A, “ECC group number” field 94B,“next allocated page number” field 94C, “page total” field 94D, “numberof pages used” field 94E, and “status” field 94F.

Index numbers for ECC group numbers within pool region PL are stored in“ECC group index number for within a pool” field 94A. Index numbers aresorted in accordance with the order of processing allocating the pagesP.

ECC group numbers are stored in the “ECC group number” field 94B.

The number of the page storing the next data from the host apparatus 2is stored in the “next allocated page number” field 94C.

Information for the total number of pages P that can be allocated withina certain ECC group is stored in the “page total” field 94D.

The number of individual pages P used allocated within a certain ECCgroup is stored in the “number of pages used” field 94E.

Information indicating the state within a certain ECC group is stored inthe “status” field 94F.

(1-2-3) Outline of Operation of Storage System

Next, a description is given of an outline of the operation of thestorage system 1 of this embodiment.

First, a description is given regarding the manner in which data fromthe host apparatus 2 is allocated to an stored in storage regions withinECC groups of this embodiment based on write requests from the hostapparatus 2.

(1-2-3-1) Write Processing at Channel Adapter

A description is now given of write processing for within the channeladapter 7 based on write requests from the host apparatus 2. This writeprocessing is executed by the channel adapter 7 based on the channeladapter write program 70.

Specifically, as shown in FIG. 11, this processing is started by thechannel adapter 7 receiving a write request from the host apparatus 2(SP0).

Next, the channel adapter 7 determines whether or not a storage locationfor the data is a base volume BVVOL allocated and correlated in pageunits to a storage region within an ECC group based on the write requestfrom the host apparatus 2 (SP1). Specifically, the channel adapter 7refers to certain virtual volume configuration information 92 in theshared memory 9 and determines whether or not a page number within anECC group correlated to the volume number of the base volume BVVOL isallocated.

When the channel adapter 7 determines that the storage region within theECC group correlated to the volume number of the base volume BVVOL is asyet unallocated (SP1: NO), allocation processing is started (SP2). Thedetails of this allocation processing executed by the channel adapter 7are described in the following.

When the allocation processing is complete, the channel adapter 7determines whether or not a storage region within the ECC groupcorrelating to the volume number of base volume BVVOL is allocated usingpage units (SP3).

When the channel adapter 7 determines that allocation of the storageregion within the ECC group in page units has failed (SP3: NO), thewrite process ends in error (SP4), the host apparatus 2 is notified, andthe processing ends (SP10). However, when it is determined thatallocation in page units is successful (SP3: YES), processing of stepSP5 is carried out.

On the other hand, in step SP1, when channel adapter 7 determines thatallocation of the storage regions within the ECC group is alreadycomplete (SP1: YES), data from the host apparatus 2 is temporarilywritten to the cache memory 10 (SP5).

Next, the channel adapter 7 determines whether or not a storage locationfor the data is a mirror volume MVVOL allocated and correlated in pageunits to a storage region within an ECC group based on the write requestfrom the host apparatus 2 (SP6). Specifically, the channel adapter 7refers to certain virtual volume configuration information 92 in theshared memory 9 and determines whether or not a page number within anECC group correlated to the volume number of the mirror volume MVVOL isallocated.

When the channel adapter 7 determines that storage regions within theECC group correlating with the volume number of the mirror volume MVVOLhave already been allocated (SP6: YES), the channel adapter 7 carriesout a stage request to the disk adapter 11 in such a manner that datafor the base volume BVVOL and mirror volume MVVOL in the cache memory 10is staged to a page number within the ECC group correlating the basevolume BVVOL and the mirror volume MVVOL (SP7).

Further, when the channel adapter 7 determines that storage regionswithin the ECC group correlated to the volume number of the mirrorvolume MVVOL are not yet allocated (SP6: NO), a destage request is madeto the disk adapter 11 in such a manner that only data of the basevolume BVOL within the cache memory 10 is destaged to the page numberwithin the correlated ECC group (SP8).

The channel adapter 7 then notifies the host apparatus 2 that the writeprocessing has finished normal (SP9), and the processing is complete(SP10).

(1-2-3-2) Disk Adapter Write Processing

A description is now given of write processing within disk adapter 11based on a write request from the host apparatus 2. This writeprocessing is executed by the channel adapter 11 based on the diskadapter write program 110.

Specifically, as shown in FIG. 12, this processing is started by thedisk adapter 11 receiving a destage request from the channel adapter 7(SP20).

Upon starting, the disk adapter 11 determines whether or not there is afault in the hard disks 50 of the ECC group taken to be storing the data(SP21).

When there is determined to be a fault in the hard disks 50 (SP21: YES),the disk adapter 11 carries out fault processing to process the ECCgroups the hard disk 50 exhibiting a fault belongs to (SP22) andprocessing to recover the ECC group the hard disk 50 exhibiting a faultbelongs to (SP23). The disk adapter 11 then writes data from the hostapparatus 2 to a page P allocated within the ECC group (SP24), and thisprocessing is complete (SP25).

On the other hand, when the disk adapter 11 determines that there are nofaults at the hard disks 50 (SP21: NO), data is written from the hostapparatus 2 to the page P allocated within the ECC group (SP24), andthis processing is complete (SP25).

When data from the host apparatus 2 is normally written to the pate Pallocated in a normal manner within the ECC group, each item ofconfiguration information is updated as shown in FIG. 13.

First, a volume number of “1” for base volume BVVOL and a volume numberof “2” for mirror volume MVVOL are adopted. Here, the pool IDcorrelating base volume BVVOL and mirror volume MVVOL is taken to be“0”. The base volume BVVOL correlates the ECC group “1” under thecontrol of pool ID “0” and page number “0” within ECC group “1”.

Similarly, mirror volume MVVOL correlates with page number “0” withinECC group “3” that is under the control of pool ID “0”.

At this time, at the page configuration information 94 configured everypool ID number, allocation is complete for page number “0” of ECC group“1” and “3”, and the value of “next allocated page number” field 94Ctherefore becomes “1”.

Further, the “number of pages used” field 94E is updated to “1” in orderto use page number “0” of ECC group “1” and “3”. In accompaniment withthis updating, the values within the “ECC group index number for withina pool” field 94A of the page configuration information 94 are “0” and“1”. These are therefore taken as the numbers “0” and “1” within“previously allocated ECC group index number” field 91C, and the virtualvolume and pool volume configuration information 91 is updated.

In the above, the flow of write processing from step SP0 to step SP25 issuch that data from the host apparatus 2 is distributed at two storageregions within the same or different ECC groups and stored.

(1-2-3-3) Allocation Processing at Channel Adapter 7

Here, in step SP2, a specific description is given of the manner inwhich the channel adapter 7 carries out allocation processing. Thisallocation processing is executed by channel adapter 7 based on theallocation program 71.

As shown in FIG. 14, in the event that the channel adapter 7 determinesthat a page P within an ECC group corresponding to the base volume BVVOLis not yet allocated to a storage region of the base volume BVVOL (SP1:NO) or in the event that an ECC group exists where a fault has occurredas described in the following, allocation processing allocating the pageP within the ECC group corresponding to the base volume BVVOL is started(SP30). The channel adapter 7 then executes allocation decidingprocessing for the base volume BVVOL (SP31). The details of thisallocation deciding processing executed by the channel adapter 7 aredescribed in the following.

The channel adapter 7 then determines whether or not allocation of thepage P within the ECC group corresponding to the base volume BVVOL tothe storage region of the base volume BVVOL is successful (SP32), andwhen it is determined that allocation has failed (SP32: NO), thisprocessing ends in error (SP33).

On the other hand, when the channel adapter 7 determines that allocationof the page P within the ECC group corresponding to the base volumeBVVOL to the storage region of the base volume BVVOL is successful(SP32: YES), the allocated ECC group number and page number are set(SP34). The channel adapter 7 then updates the corresponding locationswithin configuration information 91 for the virtual volume within theshared memory 9 and the pool volume, the virtual volume configurationinformation 92, and the page configuration information 94.

The channel adapter 7 then sets the ECC group allocated to the basevolume BVVOL as an ECC group where allocation is not possible (SP35).This is to ensure that the page P within the same ECC group as the basevolume BVVOL is not allocated to the storage region of the mirror volumeMVVOL while storing the same data.

Continuing on, the channel adapter 7 starts allocation decidingprocessing to allocate storage regions of the mirror volume MVVOL andpages P within the ECC group (SP36). The details of this allocationprocessing executed by the channel adapter 7 are described in thefollowing. The channel adapter 7 then carries out the processing fromstep SP37 to step SP39 using the same procedure as for the processing ofstep SP32 to SP35. The channel adapter 7 then allocates the page P ofthe ECC group corresponding to the mirror volume MVVOL to the storageregion of the mirror volume MVVOL, and the allocation processing iscomplete (SP40).

(1-2-3-4) Allocation Deciding Processing at Channel Adapter 7

Here, in step SP31 or step SP36, a specific description is given of themanner in which the channel adapter carries out allocation decidingprocessing. This allocation deciding processing is executed by channeladapter 7 based on the allocation deciding program 72. Here, adescription is given for deciding in what manner to allocate the pagewithin the ECC group to the storage region of the base volume BVVOL butit is taken that the same processing procedure is carried out for themirror volume MVVOL.

As shown in FIG. 15 and FIG. 16, in the event that the channel adapter 7determines that the page P within the ECC group corresponding to thebase volume BVVOL is not yet allocated to the BVVOL storage region ofthe base volume (SP1: NO), allocation deciding processing is started toallocate the storage region of the base volume BVVOL and the page Pwithin the ECC group (SP50).

The channel adapter 7 refers to the “previously allocated ECC groupindex number” field 91C of the configuration information 91 of thevirtual volume and pool volume, and determines whether or not thepreviously allocated ECC group index number corresponding to the basevolume BVVOL is valid (SP51). For example, as shown in FIG. 17, theindex number allocated the previous time is taken to be “0”.

The channel adapter 7 is allocated with the ECC group index numberallocated the previous time corresponding to the base volume BVVOL andwhen this is determined to be valid (SP51: YES), step SP53 is proceededto.

On the other hand, if the channel adapter 7 determines that a previouslyallocated ECC group index number is not inputted to the “previouslyallocated ECC group index number” field 91C and is actually “FFFF”(SP51: NO), the ECC group number that is under the control of the poolID is set to the “previously allocated ECC group index number” field 91C(SP52).

For example, when it is taken that the pool ID corresponding to virtualvolume number “1” of the base volume BVVOL and virtual volume number “2”of mirror volume MVVOL is “0”, an ECC group number of “3” that is underthe control of the pool volume PVOL0 of pool ID “0” is set.

The channel adapter 7 then substitutes the previously allocated ECCgroup index number at the ECC group index number allocated this time(SP53).

For example, as shown in FIG. 17, the previously allocated ECC groupindex number is “0”, and the ECC group number under the control of thepool volume PLVOL0 is “3”. The ECC group index numbers allocated thistime are therefore “1” and “2”. The previously allocated ECC group indexnumber “0” is then substituted in the ECC group index number for thistime. In this step, previously allocated ECC group index number becomes“0”.

The channel adapter then adds 1 to the ECC group index number allocatedthis time (SP54).

For example, as shown in FIG. 17, 1 is added to the ECC group indexnumber “0” allocated this time decided in step SP53. This thenconstitutes the start order for allocating the ECC group index number“1”.

Next, the channel adapter 7 determines whether or not the ECC groupindex number allocated on this occasion is the same as the ECC groupnumber or is a number larger than the ECC group number (SP55).

When the channel adapter 7 determines that the ECC group index numberallocated this time is the same as the ECC group number or is a numberlarger than the ECC group number (SP55: YES), the ECC group index numberis set to the beginning number of the allocation (SP56).

Here, the beginning number for allocation of the ECC group index numberis always set to “0”. The ECC group allocated this time can be allocatedto the index number within the ECC group under the control of the poolID with the exception of the ECC group index number allocated this time.

On the other hand, when it is determined that the channel adapter 7determines whether or not the ECC group index number allocated on thisoccasion is not the same as the ECC group number or is a number smallerthan the ECC group number (SP55: NO), step SP57 is proceeded to.

The channel adapter 7 then refers to the total number of pages for theECC group corresponding to the ECC group index number allocated thistime that is the beginning number and the number of pages used, anddetermines whether or not allocatable pages are present (SP57).

In the event that the channel adapter 7 determines that there are noallocatable pages (SP57: NO), step SP59 is proceeded to.

On the other hand, in the event that the channel adapter 7 determinesthat an allocatable page is present (SP57: YES), the channel adapterdetermines whether or not the ECC group number allocated on thisoccasion is an unallocatable ECC group number (SP58).

When the channel adapter 7 determines that the ECC group numberallocated this time is an unallocatable ECC group number (SP58: YES),next, the channel adapter 7 determines whether or not the ECC groupindex number allocated this time is the ECC group index number allocatedthe previous time (SP59).

In the event that the channel adapter 7 determines that the ECC groupindex number allocated this time is the ECC group index number allocatedthe previous time (SP59: YES), allocation of the page P fails becausethe ECC group is already allocated (SP60), and this processing ends(SP64).

On the other hand, when the channel adapter 7 determines that the ECCgroup index number allocated this time is not the ECC group index numberallocated the previous time (SP59: NO), step SP54 is returned to. Forexample, as the ECC index number “1” allocated this time is not the ECCgroup number “0” allocated the previous time, step SP54 is returned toagain, and processing is carried out for the ECC group index number “2”.

In step SP58, when the channel adapter 7 determines that the ECC groupnumber allocated this time is not the unallocatable ECC group number(SP58: NO), page P is allocated (SP61).

After this, the channel adapter 7 sets the ECC group index numberallocated this time as the previously allocated ECC group index number(SP62), allocation of the page P is successful (SP63), and thisprocessing is complete (SP64).

When this processing is complete (SP64), the channel adapter 7 carriesout the determination of step SP32 or step SP37 described previouslybased on the results determined in the allocation deciding processing,and allocation processing is executed.

(1-2-3-5) Disk Adapter Fault Processing

A detailed description is now given of in what manner the disk adapter11 carries out fault processing for the ECC group a hard disk 50 forwhich a fault has occurred belongs to in step SP22. The disk adapter 11executes this fault processing based on fault program 111.

When the disk adapter 11 determines that there is a fault at a hard disk50 (SP21: NO), as shown in FIG. 18, fault processing begins (SP70).

The disk adapter 11 then acquires the number of the ECC group the page Pfor which the fault has occurred belongs to from the virtual volumeconfiguration information 92 (SP71).

Next, the disk adapter 11 refers to the pool configuration information94 and acquires the begging pool ID (SP72).

The disk adapter 11 then refers to the page configuration information 94for the begging pool ID, and determines whether or not the number of theECC group the hard disk 50 where the fault occurred belongs to isregistered in the page configuration information 94 (SP73).

When the disk adapter 11 determines that the number of the ECC group thedisk 50 where a fault has occurred belongs to is registered in the pageconfiguration information 94 (SP73: YES), the “status” field of thenumber ECC group where a fault occurred for the page configurationinformation 94 is set to “fault” (SP74), and step SP75 is proceeded to.For example, page configuration information 94 for pool ID 0 is shown inFIG. 19. When a fault occurs at ECC group 1, the “status” field 94F ofECC group 1 is set to “fault”.

When the disk adapter 11 determines that the number of the ECC group thehard disk 50 where a fault has occurred belongs to is not registered inthe page configuration information 94 (SP73: NO), it is determinedwhether or not to carry out fault processing for all of the pool ID'senumerated in the pool configuration information 93 (SP75).

When the disk adapter 11 determines not to carry out fault processingfor all of the pool ID's enumerated in the pool configurationinformation 93 (SP75: NO), the next pool ID enumerated in the poolconfiguration information 93 is acquired (SP76), step SP73 is againreturned to, and fault processing is carried out for the ECC group forwhere a fault has occurred from the next pool ID.

Further, when the disk adapter 11 determines to carry out faultprocessing for all of the pool ID's enumerated in the pool configurationinformation 93 (SP75: YES), the fault processing ends (SP77).

The disk adapter 11 then ends this processing (SP77), and fault recoveryprocessing (SP23) shown in FIG. 12 is executed.

(1-2-3-6) Disk Adapter Fault Recovery Processing

Continuing on, in step SP23, a detailed description is given of faultrecovery processing to determine in what way the disk adapter 11 is torestore the allocation region allocated within the ECC group the harddisk 50 for which a fault has occurred belongs to. The disk adapter 11executes this fault recovery processing based on fault recovery program112.

In the event that the disk adapter 11 detects the number of the ECCgroup the fault has occurred for by executing the fault processingdescribed above, as shown in FIG. 20 and FIG. 21, the fault recoveryprocessing is started (SP80).

First, the disk adapter 11 refers to the virtual volume and pool volumeconfiguration information 91, and acquires the beginning virtual volumenumber (SP81). For example, in the event that the ECC group a fault hasoccurred for is ECC group 1, the numbers of the virtual volumes the ECCgroup 1 is correlated to are “1” and “2”. Therefore, in this case, thenumber for the beginning virtual volume is “1”.

Next, the disk adapter 11 refers to the virtual volume and pool volumeconfiguration information 91, and determines whether or not “pool ID”field 91B corresponding to the acquired beginning virtual volume numberis “FFFF” indicating that allocation has not yet been made or use hasnot yet taken place (SP82).

When the disk adapter 11 determines that the “pool ID” field 91Bcorresponding to the acquired beginning virtual volume number is “FFFF”indicating that allocation or use has not yet taken place (SP82: NO),step SP91 is proceeded to.

On the other hand, when the disk adapter 11 determines that the “poolID” field 91B corresponding to the acquired beginning virtual volumenumber is “FFFF” indicating that allocation or use has not yet takenplace (SP82: YES), the disk adapter 11 refers to the virtual volumeconfiguration information 92 for the number of the beginning virtualvolume, and refers to the page number of the virtual volume (SP83). Forexample, when the disk adapter 11 refers to the virtual volumeconfiguration information 92 of the virtual volume 1, the page numbersfor the virtual volume are “0”, “1” and “2”.

The disk adapter 11 then determines whether or not the ECC group numbercorresponding to the page number of the virtual volume referred to is anECC group number a fault has occurred for based on the virtual volumeconfiguration information 92 for the beginning virtual volume number(SP84).

When the disk adapter 11 determines that the ECC group numbercorresponding to the page number of the referred to virtual volume isnot an ECC group number a fault has occurred for (SP84: NO), step SP89is proceeded to.

On the other hand, when the disk adapter 11 determines that the ECCgroup number corresponding to the page number of the referred to virtualvolume is an ECC group number a fault has occurred for (SP84: YES), mainfault recovery processing is carried out (SP85). This fault recoverymain processing is described in the following.

Next, disk adapter 11 determines whether or not recovery of theallocated region is successful based on the processing results of themain fault recovery processing (SP86), and when it is determined that itis not possible to recover allocated regions within the ECC group wherethe fault has occurred (SP86: NO), notification to the effect that thereis no region it is possible to allocate to an extent where recovery ispossible is carried out (SP87), and this processing ends in error(SP88).

When the disk adapter 11 determines that the allocated region has beenrecovered from the processing results for the main fault recoveryprocessing (SP86: YES), the disk adapter 11 determines whether or not torefer as far as the page number of the final virtual volume (SP89).

When the disk adapter 11 determines that up to the page number of thefinal virtual volume is not referred to (SP89: NO), the page number ofthe next virtual volume is referred to (SP90), and with regards to theECC group number corresponding to the page number of the next virtualvolume, step SP84 is again returned to, and processing is executed.

Further, when the disk adapter 11 determines to refer as far as the pagenumber of the final virtual volume (SP89: YES), it is determined whetheror not to refer to as far as the final virtual volume number enumeratedin the virtual volume configuration information 92 (SP91).

When the disk adapter 11 then determines that referral does not takeplace up to the final virtual volume number (SP91: NO), the next virtualvolume number is referred to (SP92), and step SP82 is returned to.

In the event that the disk adapter 11 determines to refer as far as thefinal virtual volume number (SP91: YES), the fault recovery processingis complete (SP93).

After this, the disk adapter 11 then ends this processing (SP93), andSP24 shown in FIG. 12 is executed.

(1-2-3-7) Main Disk Adapter Fault Recovery Processing

Further, a detailed description is given in step SP85 with regards tothe manner in which disk adapter 11 carries out recovery processing forthe data within a region allocated for an ECC group where a fault hasoccurred. The disk adapter 11 executes this main fault recoveryprocessing based on the main fault recovery program 113.

First, when the disk adapter 11 determines that the ECC group numbercorresponding to the page number of the referred to virtual volume is anECC group number a fault has occurred for (SP84: YES), as shown in FIG.22, the disk adapter 11 starts main fault recovery processing (SP100).

The disk adapter 11 then sets the number of the ECC group where a faulthas occurred as an ECC group number where allocation is not possible(SP101). At this time, pairs of storage regions correlated with thenumber of the ECC group where a fault has occurred are also set as ECCgroup numbers where allocation is not possible. After this, the diskadapter 11 instructs the channel adapter 7 to carry out page allocationdeciding processing for the base volumes BVVOL and mirror volumes MVVOLcorrelated to the ECC group allocation is not possible for (SP102).

In accordance with this instruction, the channel adapter 7 executesprocessing from step SP30 to step SP40 and from step SP50 to step SP64.

When the disk adapter 11 receives notification of page allocationdeciding processing from the channel adapter 7 (SP103), the disk adapter11 determines whether or not it was possible to allocate pages from ECCgroups excluding the ECC group where the fault occurred (SP104), andwhen it is determined that page allocation failed (SP104: NO), thisprocessing ends with an error (SP105).

On the other hand, when the disk adapter 11 determines that it ispossible to allocate pages from ECC groups other than the ECC group afault has occurred for (SP104: YES), data is copied from the page pairedwith the page a fault has occurred for to page P the allocation issuccessful for (SP106).

For example, as shown in FIG. 23, a description is given of the casewhere an ECC group where a fault id generated is ECC group 1.

Storage regions within the base volumes BVVOL constituting the hostvolumes HVVOL are correlated with page P0 of the ECC group 1. Similarly,storage regions within the mirror volumes MVVOL constituting the hostvolumes HVVOL are correlated with page P1 of the ECC group 1.

It is not possible to use storage regions of base volumes BVVOL ormirror volumes MVVOL correlated with ECC group 1 a fault has occurredfor.

Page P2 of ECC group 2 within the storage region within base volumeBVVOL is then allocated as a result of this allocation decidingprocessing, and correspondence of page P2 of the ECC group 2 correlatedto page P0 of the ECC group 1 is changed. Similarly, Page P2 of ECCgroup 3 within the storage region within mirror volume MVVOL is thenallocated, and correspondence of page P2 of the ECC group 3 correlatedto page P1 of the ECC group 1 is changed.

Data is then copied from page P0 of the ECC group 3 storing the samedata that has a pair relationship with the page P0 of the ECC group 1 topage P2 of the newly allocated ECC group 2. Similarly for page P2 of thenewly allocated ECC group 3, data stored in page P1 of the ECC group 2is copied to page P2 of the ECC group 3. This copy processing is carriedout between ECC groups.

When copying is complete, disk adapter 11 changes the virtual volumeconfiguration information 92 (Sp107) and ends the main fault recoveryprocessing (SP108).

After this, the disk adapter 11 then ends this processing (SP108), andSP86 shown in FIG. 21 is executed.

As a result of the respective processes carried out above, the channeladapter 7 and the disk adapter 11 allocate a page within a different ECCgroup at a paired volume based on a write request from the hostapparatus 2 and it is possible to save the same data on the respectivepages. This means that even if a fault occurs at one ECC group, it ispossible to recover data by ensuring an allocated region within anotherECC group.

(1-2-3-8) Channel Adapter Read Processing

A description is now given of read processing for within the channeladapter 7 based on read requests from the host apparatus 2. This readprocessing is executed by the channel adapter 7 based on the channeladapter read program 73.

Specifically, as shown in FIG. 24, upon receiving a read request fromthe host apparatus 2, the channel adapter 7 starts read processing onthe side of the channel adapter 7 (SP110).

Next, the channel adapter 7 determines whether or not data requestedfrom the host apparatus 2 is present within the cache memory 10 (SP111).

In the event that the channel adapter 7 determines that data requestedby the host apparatus 2 is not in the cache memory 10 (SP111: NO), readsorting processing is carried out in order that the requested data savedin page P within the ECC group is read out (SP112). This read sortingprocessing is described in the following.

The channel adapter 7 determines whether or not a read out ECC groupnumber is an invalid ECC group number based on the results of the readsorting processing (SP113). When the channel adapter 7 determines thatthe ECC group number is an invalid ECC group number (SP113: YES), thehost apparatus 2 is instructed to the effect that the read processingended in error (SP114), and the read processing ends (SP118).

On the other hand, when the channel adapter 7 determines that the readout ECC group number is not an invalid ECC group number (SP113: NO), aread processing request is made to the disk adapter 11 (SP115).

After this, when the channel adapter 7 receives notification of readprocessing completion executed at the side of the disk adapter 11(SP116), the requested data is sent to the host apparatus 2 (SP117), andthe read processing ends (SP118).

In step SP111, when it is determined that data requested by the hostapparatus 2 is present in the cache memory 10 (SP111: YES), datarequested from the cache memory 10 is sent to the host apparatus 2(SP117), and the read processing ends (SP118).

(1-2-3-9) Disk Adapter Read Processing

A description is now given of read processing for in the disk adapter 11based on read requests from the host apparatus 2. This read processingis executed by the disk adapter 11 based on the disk adapter readprogram 114.

As shown in FIG. 25, when a read processing request is received from thechannel adapter 7, the disk adapter 11 starts read processing on theside of the disk adapter 11 (SP120).

The disk adapter 11 then determines whether or not there is a fault inthe hard disks 50 (SP121). When a fault is present (SP121: YES), theprocessing of step SP122 and SP123 is carried out in the same way as theprocessing procedure for steps SP22 and SP23, and step SP124 isproceeded to after fault recovery.

On the other hand, in the event that it is determined that there is nofault at the hard disks 50 (SP121: NO), the ECC group the hard disk 50storing the data requested by the host apparatus 2 is accessed (SP124),the data requested by the host apparatus 2 is read out, the channeladapter 7 is notified of completion of the read processing (SP125), andthis processing ends (SP126).

(1-2-3-10) Read Sort Processing at the Channel Adapter

A detailed description is now given of the manner in which read sortingprocessing is carried out in the channel adapter 7 based on readrequests from the host apparatus 2 in step SP112. This read sortingprocessing is executed by the channel adapter 7 based on the readsorting program 74.

Specifically, in the event that the channel adapter 7 determines thatdata requested by the host apparatus 2 is not in the cache memory 10(SP111: NO), as shown in FIG. 26 and FIG. 27, read sorting processing iscarried out in order that the requested data saved in page P within theECC group is started (SP130).

Next, the channel adapter 7 converts the address designated by the hostapparatus 2 using a read request to a page number (SP131), anddetermines whether or not the converted page number is an even number(SP132).

When the page number is an even number (SP132: YES), the channel adapter7 refers to the virtual volume and pool volume configuration information91, and acquires the pool ID correlating to the base volume BVVOL(SP133).

The channel adapter 7 acquiring the pool ID correlated to the basevolume BVVOL then refers to the page configuration information 94 in thepossession of the pool ID number, and confirms whether or not the“status” field 94F is normal (SP134).

When this is confirmed to be normal (SP134: YES), the channel adapter 7outputs the ECC group number and page number correlated to the basevolume BVVOL (SP135), and ends the read sorting processing (SP145).

When a fault is confirmed (SP134: NO), the channel adapter 7 refers tothe virtual volume and pool volume configuration information 91, andacquires the pool ID correlating to the mirror volume MVVOL (SP136).

The channel adapter 7 acquiring the pool ID correlated to the mirrorvolume MVVOL then refers to the page configuration information 94 in thepossession of the pool ID number, and confirms whether or not the“status” field 94F is normal (SP137).

When this is confirmed to be normal (SP137: YES), the channel adapter 7outputs the ECC group number and page number correlated to the mirrorvolume MVVOL (SP138), and ends the read sorting processing (SP145).

On the other hand, when a fault is confirmed (SP137: NO), the channeladapter 7 outputs an invalid ECC group number (SP139), and the read sortprocessing ends in error (SP140).

In step SP132, when the page number is an odd number (SP132: NO), thechannel adapter 7 refers to the virtual volume and pool volumeconfiguration information 91, and acquires the pool ID correlating tothe mirror volume MVVOL (SP141).

The channel adapter 7 acquiring the pool ID correlated to the mirrorvolume MVVOL then refers to the page configuration information 94 in thepossession of the pool ID number, and confirms whether or not the“status” field 94F is normal (SP142).

When this is confirmed to be normal (SP142: YES), the channel adapter 7outputs the ECC group number and page number correlated to the mirrorvolume MVVOL (SP138), and ends the read sorting processing (SP145).

On the other hand, when a fault is confirmed (SP142: NO), the channeladapter 7 refers to the virtual volume and pool volume configurationinformation 91, and acquires the pool ID correlating to the base volumeBVVOL (SP143).

The channel adapter 7 acquiring the pool ID correlated to the basevolume BVVOL then refers to the page configuration information 94 in thepossession of the pool ID number, and confirms whether or not the“status” field 94F is normal (SP144).

When this is confirmed to be normal (SP144: YES), the channel adapter 7outputs the ECC group number and page number correlated to the basevolume BVVOL (SP135), and ends the read sorting processing (SP145).

On the other hand, when a fault is confirmed (SP144: NO), the channeladapter 7 outputs an invalid ECC group number (SP139), and the read sortprocessing ends in error (SP140).

As shown in FIG. 28, an outline view is shown of the case where readsort processing is executed normally. When a host volume HVVOL isaccessed as a result of a read request from the host apparatus 2, as aresult of the read sorting processing, a first read request accesses astorage region of base volume BVVOL, a second read request accesses astorage region of mirror volume MVVOL, and a third read request accessesa storage region of the base volume BVVOL. In this way, storage regionsof base volume BVVOL or mirror volume MVVOL are used alternately and itis possible to read out data requested based on consecutive readrequests.

It is then possible to sort storage regions used by the base volumeBVVOL and mirror volumes MVVOL correlated to the ECC group storing therequested data using page numbers converted from addresses instructed bythe host apparatus 2 based on read requests from the host apparatus 2.

In the above, a description is given of the flow of a series of writeprocesses and read processes occurring at the storage system 1 of thisembodiment.

(1-2-3-11) Allocation Processing in the Case of Adding an ECC Group

Next, a description is given for the storage system 1 of this embodimentof a modified example of allocation processing allocating data storedwithin a certain ECC group to within an added ECC group in the eventwhere the ECC group is added.

The disk adapter 11 executes this fault recovery processing based on theaddition allocation program 115.

In the event that the disk adapter 11 detects the number of the ECCgroup the fault has occurred for by executing the fault processing instep SP23, as shown in FIG. 29 and FIG. 30, the fault recoveryprocessing is started (SP150).

Next, the disk adapter 11 refers to the host volume configurationinformation 90, and acquires a virtual volume number for the beginningmirror volume MVVOL (SP151). For example, the virtual volume number ofthe beginning mirror volume MVVOL is “2”, as shown in the host volumeconfiguration information 90 and the virtual volume and pool volumeconfiguration information 91 of FIG. 31.

The disk adapter 11 then refers to the virtual volume configurationinformation 92 of the virtual volume number from the acquired virtualvolume number, and acquires the beginning page number for the “pagenumber” field 92A (SP152).

The disk adapter 11 then determines whether or not the ECC group numbercorresponding to the acquired page number is “FFFF” indicating noallocation or use as of yet (SP153).

When the disk adapter 11 determines that the ECC group numbercorresponding to the acquired page number is “FFFF” indicating noallocation or use as yet (SP153: NO), step SP159 is proceeded to, andprocessing is executed for the next page number.

On the other hand, when the disk adapter 11 determines that the ECCgroup number corresponding to the acquired page number is not “FFFF”indicating no allocation or use as of yet (SP153: YES), it is determinedwhether or not the number of the ECC group the page number constitutinga mirror configuration with the acquired page number belongs to is“FFFF” (SP154). For example, as shown in FIG. 31, when the virtualvolume configuration information 92 of virtual volume number “2” isreferred to, the page number that is “FFFF” is “2”. That constituting apair with page number “1” of the virtual volume can be understood to bepage number “1” of virtual volume number “1” by referring to the hostvolume configuration information 90 and the virtual volume configurationinformation 92. The page number 1 of virtual volume 1 can be understoodto correlate to page P149 of ECC group 1.

When the disk adapter 11 determines that the ECC group number the pagenumber constituting a mirror configuration with the acquired page numberbelongs to is “FFFF” (SP154: YES), step SP159 is proceeded to, andprocessing is executed for the next page number.

When the disk adapter 11 determines that the ECC group number the pagenumber constituting a mirror configuration with the acquired page numberbelongs to is not “FFFF” (SP154: NO), the main fault recovery processingis executed (SP155). The disk adapter 11 then copies the data to the ECCgroup added in the processing procedure for step SP100 to SP108 for theECC group number the page number constituting a mirror configurationwith the acquired page number belongs to. For example, as shown in FIG.32, data stored in the page P149 of the ECC group 1 correlated to astorage region of the base volume is copied to page P0 of the EGG group4. Then, as shown in FIG. 31, the “ECC group number” field 92Bcorresponding to “page” number 1 of the virtual volume configurationinformation 92 for virtual volume number “2” is updated to “4” and the“page numbers within an ECC group” field 92C is updated to “0”. Further,“ECC number” 93B field of the pool volume configuration information 93is updated from “3” to “4”. Moreover, “3” is added to the “ECC groupindex number for within a pool” field 94A of the page configurationinformation 94.

The disk adapter 11 then determines whether or not recovery of datastored in the ECC group is successful based on this main fault recoveryprocess (SP156). When the disk adapter 11 determines that there is afault in recovery (SP156: NO), the user is notified of this (SP157), andthis fault recovery processing ends in error (SP158).

On the other hand, in the event that the disk adapter 11 determines thatdata recovery is successful (SP156: YES), the disk adapter 11 determineswhether or not to refer as for as the final page number at the virtualvolume configuration information 92 corresponding to the virtual volumenumber of the mirror volume MVVOL (SP159).

When the disk adapter 11 determines that as far as the final page numberis not referred to (SP159: NO), the disk adapter 11 refers to the pagenumber of the next virtual volume (SP160), and the processing procedureof step SP153 is carried out again.

When the disk adapter 11 determines that as far as the final page numberis referred to (SP159: YES), the fault recovery process ends (SP161).

As described above, it is also possible to save the same data on pageswithin different ECC groups in cases where an ECC group is added.

(1-3) Effects of the First Embodiment

As described above, it is possible to allocate storage regions within anECC group based on write requests from host apparatus by utilizing anAOU function. Because of this, it is possible to save the same data indifferent ECC groups at base volumes and mirror volumes that constitutea mirror configuration and the reliability and fault tolerance of harddisks saving data can therefore be improved.

(2) Second Embodiment

Next, a storage system of a second embodiment is described in thefollowing. In the second embodiment, aspects of the configuration thatare the same as for the first embodiment are given the same numerals.Only aspects of the configuration that are different to the firstembodiment are described in the description of the second embodiment.

(2-1) Physical and Logical Configuration of Storage System

As shown in FIG. 33, shared memory 900 of a storage system 200 of thesecond embodiment is comprised of virtual volume and pool volumeconfiguration information 91, virtual volume configuration information92, pool volume configuration information 93, and page configurationinformation 94.

As shown in FIG. 34, with the logical configuration of the storagesystem 200 of the second embodiment, one pool region is configured fromthree ECC groups PL3 but a pool region PL may be configured from one ora plurality of ECC groups.

A plurality of pool volumes PLVOL may also form one pool region PL. Apool volume PLVOL may be dynamically allocated with a storage region ofthe hard disks 50 so as to supply a virtual volume VVOL. Minimum storageregions referred to as pages P that can be allocated with an ECC groupare correlated at storage regions of the virtual volume.

(2-2) Distributed Storage Function and AOU Function of Storage System

Next, a description is given of a distributed storage function and AOUfunction mounted on the storage apparatus 4 within the storage system 1.The feature of the storage system 200 of this embodiment is thatconsecutive data from the host apparatus 2 can be distributed at storagelocations in such a manner as to be stored at storage regions other thanfor the page of the ECC group storing data the previous time based onwrite requests from the host apparatus 2. For example, this refers to afunction where, in the event that there is consecutive data 1 to data 3,when data 1 is stored in page P9 of ECC group 1, data 2 is stored in apage other than page P0 of ECC group 1, and data 3 is stored in astorage region other than the page P of the ECC group storing data 1 anddata 2.

Further, an AOU function in this embodiment is a function of dynamicallyallocating virtual volumes VVOL recognized by the host apparatus 2 fromthe pool region PL (pool volume PLVOL).

(2-2-1) Write Processing at Channel Adapter

A description is now given of write processing for within the channeladapter 7 based on write requests from the host apparatus 2. This writeprocessing is executed by the channel adapter 7 based on the channeladapter write program 70.

Specifically, as shown in FIG. 35, this processing is started by thechannel adapter 7 receiving a write request from the host apparatus 2(SP170).

Next, the channel adapter 7 determines whether or not a storage locationfor the data is a virtual volume VVOL allocated and correlated in pageunits to a storage region within an ECC group based on the write requestfrom the host apparatus 2 (SP171). Specifically, the channel adapter 7refers to certain virtual volume configuration information 92 within theshared memory 9 and determines whether or not a page number within anECC group correlated to the volume number of the virtual volume VVOL isallocated.

When the channel adapter 7 determines that the storage region within theECC group correlated to the volume number of the virtual volume VVVOL isas yet unallocated (SP171: NO), allocation processing is started(SP172). The details of this allocation processing executed by thechannel adapter 7 are described in the following.

When the allocation processing is complete, the channel adapter 7determines whether or not a storage region within the ECC groupcorrelating to the volume number of virtual volume VVOL is allocatedusing page units (SP173).

When the channel adapter 7 determines that allocation of the storageregion within the ECC group in page units has failed (SP173: NO), thewrite process ends in error (SP174), the host apparatus 2 is notified,and the processing ends (SP175). However, when it is determined thatallocation in page units is successful (SP173: YES), processing of stepSP175 is carried out.

On the other hand, in step SP171, when channel adapter 7 determines thatallocation of the storage regions within the ECC group is alreadycomplete (SP171: YES), data from the host apparatus 2 is temporarilywritten to the cache memory 10 (SP175).

The channel adapter 7 the carries out a destage request to the diskadapter 11 in such a manner that data of the virtual volume VVOL withinthe cache memory 10 is destaged to a page number within an ECC groupcorrelating to the virtual volume VVOL (SP176).

The channel adapter 7 then notifies the host apparatus 2 that the writeprocessing has finished normal (SP177), and the processing is complete(SP178).

(2-2-2) Write Processing at Disk Adapter

A description is now given of write processing within disk adapter 11based on a write request from the host apparatus 2. This writeprocessing is executed by the channel adapter 11 based on the diskadapter write program 110.

Specifically, as shown in FIG. 36, this processing is started by thedisk adapter 11 receiving a destage request from the channel adapter 7(SP180).

The disk adapter 11 then writes data from the host apparatus 2 to thepage P allocated within the ECC group (SP181), and this process iscomplete (SP182).

(2-2-3) Allocation Processing at Channel Adapter

Here, in step SP172, a specific description is given of the manner inwhich the channel adapter 7 carries out allocation deciding processing.This allocation deciding processing is executed by channel adapter 7based on the allocation deciding program 72.

As shown in FIG. 37 and FIG. 38, in the event that the channel adapter 7determines that the page P within the ECC group corresponding to thevirtual volume VVOL is not yet allocated to the VVOL storage region ofthe virtual volume (SP1: NO), allocation deciding processing is startedto allocate the storage region of the base volume BVVOL and the page Pwithin the ECC group (SP190).

The channel adapter 7 carries out the same processing procedure for SP50to SP57 as the processing of step SP191 to SP197 for the virtual volumeVVOL.

The channel adapter 7 then refers to the total number of pages for theECC group corresponding to the ECC group index number allocated thistime that is the beginning number and the number of pages used, and whenit is determined that allocatable pages are present (SP197: YES), thechannel adapter 7 allocates page P (SP199).

After allocating page P, the channel adapter 7 sets the ECC group indexnumber allocated this time as the previously allocated ECC group indexnumber (SP200), allocation of the page P is successful (SP201), and thisprocessing is complete (SP203).

On the other hand, in step SP197, when the channel adapter 7 determinesthat a page capable of allocation is not present (SP197: NO), thechannel adapter 7 determines whether or not the ECC group index numberallocated this time is the ECC group index number allocated the previoustime (SP198).

In the event that the channel adapter 7 determines that the ECC groupindex number allocated this time is the ECC group index number allocatedthe previous time (SP198: YES), allocation of the page P fails becausethe ECC group is already allocated (SP202), and this processing ends(SP203).

On the other hand, when the channel adapter 7 determines that the ECCgroup index number allocated this time is not the ECC group index numberallocated the previous time (SP198: NO), step SP194 is returned to, andprocessing is continued for the index number of the next ECC group.

(2-3) Effects of the Second Embodiment

As described above, it is possible to allocate storage regions within anECC group based on write requests from host apparatus by utilizing anAOU function.

Because of this, at the storage regions of the virtual volume, it ispossible to store consecutive data in a distributed manner correlatedwith pages of ECC groups other than the pages of ECC groups storing onthe previous occasion, and the throughput performance of the hard disksaving the data can therefore be improved.

(3) Third Embodiment

Next, a storage system of a third embodiment is described in thefollowing. In the third embodiment, aspects of the configuration thatare the same as for the first embodiment are given the same numerals.Only aspects of the configuration that are different to the firstembodiment are described in the description of the third embodiment.

(3-1) Physical and Logical Configuration of Storage System

As shown in FIG. 39, first storage apparatus 4′ of a storage system 300of the third embodiment has a different configuration to theconfiguration of the channel adapter 7 of the storage apparatus 4 of thestorage system 1 of the first embodiment. In addition to the firststorage apparatus 4′, the storage system 300 is configured with secondstorage apparatus 40 connected via the network 3.

Then, as shown in FIG. 40, within the channel adapter 700, in additionto the various programs 70 to 74 described in the first embodiment, acopy program 75 is provided for copying data of the hard disks 50 toother hard disks.

In addition, as shown in FIG. 41, the logical configuration of thestorage system 300 of this embodiment is such that, of the logicalvolumes LDEV2 to LDEVm formed on the storage regions of the plurality ofhard disks at the second storage apparatus 40, the logical volume LDEV2is shown at the logical configuration for FIG. 4 in the firstembodiment.

(3-2) Copy Processing at Channel Adapter

A detailed description is now given of copy processing to back up datasaved within the ECC group of the first storage apparatus 4′ to thelogical volume LDEV2 of the second storage apparatus 40 at the same timeas reading out data saved within the ECC group of the first storageapparatus 4′ based on a read request from the host apparatus 2. Thiscopy processing is executed by channel adapter 7 based on the copyprogram 75.

Specifically, as shown in FIG. 42 and FIG. 43, the channel adapter 700starts copy processing when there is a read request from the hostapparatus 2 (SP210).

Next, the channel adapter 700 converts the address of the copy sourcedesignated by the host apparatus 2 using a read request to a page number(SP211), and determines whether or not the converted page number is anodd number (SP212).

When the page number is an odd number (SP212: YES), the channel adapter700 refers to the virtual volume and pool volume configurationinformation 91, and acquires the pool ID correlating to the base volumeBVVOL (SP213).

The channel adapter 700 acquiring the pool ID correlated to the basevolume BVVOL then refers to the page configuration information 94 in thepossession of the pool ID number, and confirms whether or not the“status” field 94F is normal (SP214).

In the event that this is configured to be normal (SP214: YES), thechannel adapter 700 implements copying from base volume BVVOL to thelogical volume LDEV2 within the second storage apparatus 40 (SP215).

The channel adapter 700 then determines whether or not to implementcopying as far as the final page number (SP216), and when it isdetermined not to implement copying as far as the final page number(SP216: NO), step SP211 is again returned to, and copying is implementedfor the next page number.

On the other hand, when the channel adapter 700 determines that copyingis implemented as far as the final page number (SP216: YES), thisprocessing ends (SP226).

In step SP214, when a fault is confirmed (SP214: NO), the channeladapter 700 refers to the virtual volume and pool volume configurationinformation 91, and acquires the pool ID correlating to the mirrorvolume MVVOL (SP217).

The channel adapter 700 acquiring the pool ID correlated to the mirrorvolume MVVOL then refers to the page configuration information 94 in thepossession of the pool ID number, and confirms whether or not the“status” field 94F is normal (SP218).

In the event that this is configured to be normal (SP218: YES), thechannel adapter 700 implements copying from mirror volume MVVOL to thelogical volume LDEV2 within the second storage apparatus 40 (SP219), andthe processing of step SP216 is then implemented.

On the other hand, when a fault is confirmed (SP218: NO), the channeladapter 700 outputs an invalid ECC group number (SP220), and the copyprocessing ends in error (SP221).

In step SP212, when the page number is an even number (SP212: NO), thechannel adapter 700 refers to the virtual volume and pool volumeconfiguration information 91, and acquires the pool ID correlating tothe mirror volume MVVOL (SP222).

The channel adapter 700 acquiring the pool ID correlated to the mirrorvolume MVVOL then refers to the page configuration information 94 in thepossession of the pool ID number, and confirms whether or not the“status” field 94F is normal (SP223).

In the event that this is configured to be normal (SP223: YES), thechannel adapter 700 implements copying from mirror volume MVVOL to thelogical volume LDEV2 within the second storage apparatus 40 (SP219), andthe processing of step SP216 is then implemented.

On the other hand, when a fault is confirmed (SP223: NO), the channeladapter 700 refers to the virtual volume and pool volume configurationinformation 91, and acquires the pool ID correlating to the base volumeBVVOL (SP224).

The channel adapter 700 acquiring the pool ID correlated to the basevolume BVVOL then refers to the page configuration information 94 in thepossession of the pool ID number, and confirms whether or not the“status” field 94F is normal (SP225).

In the event that this is configured to be normal (SP225: YES), thechannel adapter 700 implements copying from base volume BVVOL to thelogical volume LDEV2 within the second storage apparatus 40 (SP215), andthe processing of step SP216 is then implemented.

On the other hand, when a fault is confirmed (SP225: NO), the channeladapter 700 outputs an invalid ECC group number (SP220), and the copyprocessing ends in error (SP221).

(3-3) Effects of the Third Embodiment

In the above, as a result of utilizing an AOU function, it is possibleto save the same data in different ECC groups at base volumes and mirrorvolumes that constitute a mirror configuration and the reliability andfault tolerance of hard disks saving data can therefore be improved.

Further, within one storage apparatus, it is possible to improve thesystem efficiency of the storage system because use is possible withinone storage apparatus divided between ECC groups utilized in reading outbased on read requests from a host, and ECC groups utilized in copyingfor backing up to another storage apparatus.

(4) Other Embodiments

The various processes described in the first to third embodiments arecarried out by the channel adapter 7 and the disk adapter 11 but thevarious processing can be carried out by either of the channel adapteror the disk adapter 11 and are not limited to the subject describedabove.

Further, shared memory 9 is provided as first correlating sectioncorrelating a plurality of RAID groups (ECC groups) comprised of aplurality of physical disks (hard disks 50) and a pool region P and asecond correlating section correlating the pool region PL and storageregions of the virtual volume VVOL but the first correlating section andthe second correlating section may be configured from individualhardware.

A first allocating section allocating first data from the host apparatus2 to pages P of a first storage region of the first RAID group based onwrite requests from the host apparatus 2 and a second allocation sectionallocating second data from the host apparatus in a distributed mannerto storage regions of and of the RAID groups with the exception of pagesP that are at the first storage region of the first RAID group allocatedby the first allocation section are provided within the storageapparatus 4 but the first allocation section and the second allocationsection may also be provided using separate hardware configurations.

Further, a first reading section for reading out first requested datafrom RAID group regions correlating storage regions of base volumesBVVOL and mirror volumes MVVOL and a second reading section for readingout second requested data from storage regions of RAID groupscorrelating storage regions with the exception of storage regions forbase volumes BVVOL and mirror volumes MVVOL used by the first readingsection are provided within the storage apparatus 4 but the firstreading section and the second reading section may also be provided asseparate hardware configurations.

The third allocating section is taken to be an logical volume LDEV2within the second storage apparatus 50 but may also be provided at thefirst storage apparatus 4′.

The addition allocation section is provided within the storage apparatus4 but may also be provided as a separate hardware configuration.

The present invention may be broadly applied to storage systems havingone or a plurality of storage devices or to other embodiments of storagesystems.

While the invention has been described with respect to a limited numberof embodiments, those skilled in the art, having benefit of thisdisclosure, will appreciate that other embodiments can be devised whichdo not depart from the scope of the invention as disclosed herein.Accordingly, the scope of the invention should be limited only by theattached claims.

1. A storage system allocating some or all of storage regions suppliedby physical disks storing data from host apparatus as a pool region, andforming virtual volumes dynamically allocated from the pool regions,comprising: a first correlating section for correlating a plurality ofRAID groups composed of a plurality of the physical disks, and the poolregion; a second correlating section for correlating the pool region andthe storage regions of the virtual volumes; a first allocation sectionfor allocating first data from the host apparatus to a first storageregion of a first RAID group based on write requests from the hostapparatus; and a second allocation section for distributing second datafrom the host apparatus at and allocating the second data to any storageregions of the RAID groups, with the exception of the first storageregion of the first RAID group allocated by the first allocationsection, based on write requests from the host apparatus.
 2. The storagesystem according to claim 1, wherein the first correlating section:correlates a plurality of RAID groups comprising a plurality of physicaldisks, and the pool region comprised of one or a plurality of poolvolume storage regions; and the second correlating section: correlatesthe pool region comprising one or a plurality of pool volume storageregions and the virtual volume storage regions.
 3. The storage systemaccording to claim 1, having a controller for controlling the storageregions supplied by the physical devices for storing data from the hostapparatus, and the controller executing processing at the firstallocation section and the second allocation section.
 4. The storagesystem according to claim 1, wherein the virtual volume is a mirrorconfiguration comprising a base volume and a mirror volume.
 5. Thestorage system according to claim 4, wherein the first allocationsection: allocates the first data from the host apparatus to a firststorage region of the first RAID group correlated to storage regions ofthe base volume based on a write request from the host apparatus; andcorrelates back-up data for the first data from the host apparatus withthe storage regions of the mirror volume, and allocates the back up datafor the first data to any of the storage regions of the RAID groups withthe exception of the first storage region of the first RAID group. 6.The storage system according to claim 4, further comprising: a firstreading section for reading out first requested data from storageregions of the RAID group correlated with storage regions of the basevolume or the mirror volume based on read requests from the hostapparatus; and a second reading section for reading out second requesteddata from storage regions of the RAID group correlated with storageregions with the exception of storage regions of the base volume or themirror volume used by the first reading section based on read requestsfrom the host apparatus, wherein consecutive data requested from thehost apparatus is alternately read out from the base volume or mirrorvolume correlated with the storage regions storing the requested dataand sorted.
 7. The storage system according to claim 4, furthercomprising a fault processing section for, in the event that a faultoccurs at the physical disk, detecting storage regions of the RAID groupthe physical disk a fault has occurred for belongs to and processing thefault of the RAID group; and a detection section for detecting storageregions of the RAID group the physical disk having a fault belongs toand storage regions of the RAID group of the mirror configuration. 8.The storage system according to claim 7, further comprising a thirdallocating section for allocating any storage regions of any of the RAIDgroup with the exception of storage regions of the RAID group allocatedby the first allocation section and the second allocation section; and acopy section for copying data, detected by the detection section, storedin storage regions of the RAID group that is of a mirror configuration,to storage regions of the RAID group allocated by the third allocatingsection.
 9. The storage system according to claim 4, further comprisingan addition allocation section for, when a new RAID group is made byadding to the physical disk storing data from the host apparatus,allocating data stored in storage regions of the RAID group correlatedwith any of the storage regions of the base volume or mirror volume tostorage regions of the new RAID group in such a manner that any of thestorage regions of the base volume or the mirror volume and storageregions of the new RAID group adopt a mirror configuration.
 10. A datamanagement method for a storage system allocating some or all of storageregions supplied by physical disks storing data from host apparatus as apool region, and forming virtual volumes dynamically allocated from thepool regions, comprising: a first correlation step of correlating aplurality of RAID groups composed of a plurality of the physical disks,and the pool region; a second correlation step of correlating the poolregion and the storage regions of the virtual volumes; a firstallocation step of allocating first data from the host apparatus to thefirst storage region of the first RAID group based on write requestsfrom the host apparatus; and a second allocation step of distributingsecond data from the host apparatus at and allocating the second data toany storage regions of the RAID group, with the exception of the firststorage region of the first RAID group allocated in the first allocationstep, based on write requests from the host apparatus.
 11. The datamanagement method according to claim 10, wherein the first correlationstep: correlates a plurality of RAID groups comprising a plurality ofphysical disks, and the pool region comprised of one or a plurality ofpool volume storage regions; and the second correlation step: correlatesthe pool region comprising one or a plurality of pool volume storageregions and the virtual volume storage regions.
 12. The data managementmethod according to claim 10, having a controller for controlling thestorage regions supplied by the physical devices for storing data fromthe host apparatus, wherein the controller carries out the firstallocation step and the second allocation step.
 13. The storage systemaccording to claim 10, wherein the virtual volume is a mirrorconfiguration comprising a base volume and a mirror volume.
 14. The datamanagement method according to claim 13, wherein the first allocationstep: allocates the first data from the host apparatus to a firststorage region of the first RAID group correlated to storage regions ofthe base volume based on a write request from the host apparatus; andcorrelates back-up data for the first data from the host apparatus withthe storage regions of the mirror volume, and allocates the back up datafor the first data to any of the storage regions of the RAID groups withthe exception of the first storage region of the first RAID group. 15.The data management method according to claim 13, further comprising: afirst reading step of reading out first requested data from storageregions of the RAID group correlated with storage regions of the basevolume or the mirror volume based on read requests from the hostapparatus, and a second reading step of reading out second requesteddata from storage regions of the RAID group correlated with storageregions with the exception of storage regions of the base volume or themirror volume used by the first reading section based on read requestsfrom the host apparatus, wherein consecutive data requested from thehost apparatus is alternately read out from the base volume or mirrorvolume correlated with the storage regions storing the requested dataand sorted.
 16. The data management method according to claim 13,further comprising a fault processing step of, in the event that a faultoccurs at the physical disk, detecting storage regions of the RAID groupthe physical disk a fault has occurred for belongs to and processing thefault of the RAID group; and a detection step of detecting storageregions of the RAID group the physical disk having a fault belongs toand storage regions of the RAID group of a mirror configuration.
 17. Thedata management method according to claim 16, further comprising a thirdallocating step of allocating any storage regions of any of the RAIDgroup with the exception of storage regions of the RAID group allocatedin the first allocation step and the second allocation step; and a copystep of copying data, detected in the detection step, stored in storageregions of the RAID group that is of a mirror configuration, to storageregions of the RAID group allocated by the third allocating step. 18.The data management method according to claim 13, further comprising anaddition allocation step for, when a new RAID group is made by adding tothe physical disk storing data from the host apparatus, allocating datastored in storage regions of the RAID group correlated with any of thestorage regions of the base volume or mirror volume to storage regionsof the new RAID group in such a manner that any of the storage regionsof the base volume or the mirror volume and storage regions of the newRAID group adopt a mirror configuration.